View MX86250_4655731.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

MX86250 1 p/n:pm0387 rev. 1.1, jul 26, 1996 the advanced 64-bit windows-95 and directdraw accelerator 1. introduction the MX86250 is a new generation of fully integrated graphics and video accelerator. on a single chip, it inte- grates a 64-bit graphics coprocessor, a true-color video processor, 135 mhz ramdac and dual programmable clock synthesizer. the MX86250 not only delivers extreme high performance in conventional gui acceleration, it also provides very rich functionality for motion video applica- tions. the MX86250 true color video processor allows full screen full motion playback of avi and mpeg video from software based codec's such as mpeg, cinepak and indeo. for even higher quality mpeg video playback, the MX86250 media port supports the vmi connector link- ing to an external mpeg-1 decoder chip. the media port also provides for playback and capture of live video input from tv tuner or video camera. one key design goal of the MX86250 is to achieve the highest possible memory bandwidth in the display memory subsystem using main stream and cost effec- tive edo dram chips. by applying the risc design tech- nique of super pipelining, the MX86250 graphics coprocessor can execute one bitblt operation in every clock cycle. when running at 50 mhz and above, using - 50 or faster edo dram ( 20ns page mode cycle time), the bandwidth can reach 400 mb/sec and above. this extremely high bandwidth gives top-notch windows gui performance and fast frame rate in motion video play- back. for mainstream software codec delivered video play- back, the MX86250 provides video acceleration by a second gener ation video processor consisting of yuv to rgb converter, scaler, and two dimensional bilinear filter. the scaler can zoom the video windows at arbi- trary ratios. the bilinear filter provides both horizontal and vertical interpolation which is absent from 1st genera- tion video chips. for windows 95 games, the MX86250 supports directdraw with a rich set of features such as fast trans- parent blts, double buffering and page flipping so that windows 95 based games can achieve high speed sprite animation. 1.1 features high performance 64 bit graphics coprocessor ? uniformly accelerated graphics operations in all pixel formats : 256 color, high color and true color ? optimized graphics engine for bitblts, rectangle fill, pattern fill, line draw, color expansion, text transfer, and clipping ? raster operations (rops) with 3 operand bitblt alu ? one chip 8x8x24 pattern memory achieves highest thrughput in the most common bitblt in windows the pattern blt ? deep on-chip source and destination fifos for sus tained burst cycles in bitblts ? double buffered coprocessor registers allows concur rent processing with cpu ? built in hardware cursor extremely high bandwidth ? achieves single clock cycle dram access in graphics processor, video processor and display processor ? provides 400 mb/sec memory bandwidth using -50 edo dram chips ? even higher performance can be achieved by using - 35 edo dram for 533 mb/sec bandwidth which is comparable to synchronous dram fully integrated for lower system cost ? integrated 24 bit true color ramdac supports 135 mhz pixel rate and 256x18 look-up table with high color and true color bypass mode support ? integrated dual clock synthesizers ? glueless pci local bus interface ? two wire interface to eeprom, vesa ddc inter face or i 2 c channel flexible display memory configuration ? 1,2, or 4 mb display memory. ? 256k x 4, 256k x 8, and 256k x 16 dual cas or dual we dram. ? fast-page and hyper-page edo
2 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 motion video codec acceleration ? yuv/ycrcb conversion of industry standard yuv 4.2.2 or 2.1.1 formats ? non-integer zoom in both x and y direction ? interpolation with bi-linear filters in both horizontal and vertical dimensions ? color key supports video overlay, chroma key sup ports transparency effect or blue screen video ? edge blending for smooth looking blue screen video ? video window is double buffered for smooth video play back. ? independent video window mode allowing true-color video, independent of graphics color depth. windows 95 game acceleration ? designed to accelerate windows 95 direcdraw for game acceleration ? fast transparent bitblt for sprite animation ? linear access to offscreen directdraw surface storing multiple sprites ? double buffer to support page flipping which is syn chronized to vertical retrace media port interface to mpeg decoder chips or video capture frontend ? glueless interface to vmi (video module interface) connector to allow plug-in daughtercard of hardware mpeg-1 support ? glueless interface to phillips 7110 for live video input ? dual aperture for simultaneous access to display memory from graphics and video ? built in fifo and flexible decimator high speed pci local bus ? support zero wait state pci burst cycles for maximum cpu write bandwidth ? support version 2.1 pci disconnect and retry cycles to free cpu from status polling overhead ? level command and data fifo unified memory architecture (uma) support ? support vesa uma (vuma) standard ? programmable wait states in dram access cycles to work with slower main memory dram chips ? dram interface buffers have programmable drive strength for optimal power versus performance tradeoff extended display resolution support ? 1600x1200, 64k color (int) ? 1280x1024, 64k color @ 75 hz ? 1024x768, 16m color @ 60 hz "green pc" power management ? support vesa dpms (display power management) standard ? built in advanced power management techniques such as internal dac power down mode and clock idle modes multiple peripheral interfaces ? vesa display data channel (ddc-2b) protocol support ? two wire eeprom interface ?i 2 c channel ? vesa standard and advanced feature connector (vafc) support ? general purpose i/o pins complete hardware compatibility ? windows 95 plug and play compliant ? vga hardware, register, and bios compatible ? pci revision 2.1 compatible low-power 0.5 um cmos technology 208 pin pqfp package
3 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 2.functional description this chapter describes the architecture and function blocks of te architecturtecture and function blocks of the MX86250. 2.1 overview the MX86250 architecture is described in figure 2.1, MX86250 function block diagram. as shown in the diagram, the major function blocks are as follows : ? 64 bit graphics co-processor ? memory controller ? pci bus interface unit ? video processor ? media port ? true color ramdac ? dual clock synthesizer ? ddc/i 2 c/eeprom interface ports ? vga controller the function block modules are connected with 64-bit buses. multiple fifos buffer data flows within the tight pipeline structures allowing concurrent operations and maximum bandwidth. figure 1 : MX86250 function block diagram pci bus interface unit pci bus ddc 12c eeprom dual clock synthsizer peripheral interface ports gx controller scaler & filters hardware cursor dclk mclk gx/video fifo crt controller attribute controller vga sequencer display process command/data fifo scaler & filters color converter source fifo rop alu memory controller destination fifo pattern map video processor ture color ram dac r.g.b dram interface vmi connector medio port graphics processor
4 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 2.2 64-bit graphics co-processor the MX86250 graphics co-processor accelerates com- mon graphics user interface drawing functions , includ- ing bitblt, rectangle fill, pattern fill, bresenham line draw, and text transfer. hardware clipping and hardware cursor further reduce software driver overhead, includ- ing bitblt, rectangle fill, pattern fill, bresenham line draw, and text transfer. hardware clipping and hardware cursor further reduce software driver overhead to the minimum. the graphics co-processor supports scrardware cursor further rr further reduce software driver overhead to the minimum. the graphics co-processor supports screen widths of 640, 800, 1024, 1152, 1280, 1600 and 2048. pixel depth can be 8, 16, and 32 bits. the display memory size can be 1,2 or 4 megabytes. all co-processor drawing opera- tions are programmed with 32 bit registers in a linear address aperture. three operand bitblt the graphics co-processor executes bitblt operations between three operands: the source bitmap, the desti- nation bitmap, and the pattern bitmap. there are 256 op- erations on bitmaps, called raster operations (rop). an alu with three operand inputs is implemented to execute any of the 256 ro p s in a single cycle, unlike earlier generation gui chips which used only two operands and implemented only 16 rops. this forced the software driver to decompose those 3-operand bitblt into two or three 2-operand bitblts significantly slowing down the drawing process. source/destination fifos the three inputs to the bitblt alu are from the source fifo, the destination fifo and the pattern map buffer. the source and destination fifo are 64 bit wide and 8 levels deep. they allow the fetch cycles for source and destination pixels to be run in page mode cycles. by hav- ing destination fifo, the MX86250 can run destination read-modify-write operations in page mode reads followed by page mode writes which is substantially faster than the read-modify-write cycles in an edo-dram based system. pattern map buffer the most common bitblt operation in windows is the patblt which means painting a large window background using a brush which is an 8 by 8 pattern bitmap. many gui chips store the brush pattern bitmap in offscreen memory. during patblt, the pattern are fetched repeat- edly. to accelerate patblt, the MX86250 has on-chip memory to store a full 8 by 8 pattern bitmap. unlike others which can only store 8-bit pixels, the MX86250 can store pixel maps of 8, 16, and 32 bit pixels. this complete imple- mentation of pattern map, enables the MX86250 to ex- ecute the patblts at peak memory bandwidth using a long burst of page mode writes and thus achieving the best drawing performance. text / font drawing acceleration drawing text characters or fonts are another very com- mon windows drawing operation. the fonts are mono- chrome bitmaps that get expanded into color pixel maps in the graphics co-processor. the MX86250 optimizes this process in several ways. font bitmaps can be stored in system memory and trans- ferred to the co-processor for color expansion.the MX86250 provides a screen port to facilitate this memory to screen transfer. the screen port is mapped in a linear address aperture of 64k bytes. the monochrome font pixels are buffered in the source fifo so that concur- rent operations are enabled for font transfer from system memory and color expansion in the co-processor. the display driver can also cache font bitmaps in offscreen memory using the so called font-cache scheme. the MX86250 provides direct support of offscreen packed monochrome bitmap to color map expansion. this op- eration greatly accelerates the performance of font cache. windows 95 direct draw acceleration windows 95 direct draw is aimed to turn the windows gui environment into a game platform with high speed sprite animation. the key to sprite animation is transpar- ent blt. the MX86250 implements a flexible color key mechanism to enable high speed transparent blt. a trans- parent blt writes to screen a source bitmap, that is, a sprite, which is in an irregular shape such as a cartoon
5 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 figure. the background pixels which should not be over- written are coded in the special key color. the color com- pare function block in the graphics co-processor checks each pixel against the key color. if a match is found, the pixel is not written, preserving the background around the sprite. thus, an irregular shape is blted using a fast rectangle draw. in the MX86250, the color key can be in the source or the destination bitmap. transparent blt uses source color key. the destination color key can be used to protect screen areas. a mask register is defined to allow the key color be a range of color values instead of a single value. 2.3 memory controller the MX86250 memory controller module interfaces to the frame buffer dram chips which can operate in either fast page mode, or extended data out (edo) mode. the frame buffer size can be 1, 2, or 4 megabytes. industry standard 256k by 4, by 8, or by 16 dram chips are sup- ported. the memory controller performs the page mode cycle in either 2 clock cycle or 1 clock cycle, depending on the dram types being used. the highest bandwidth is delivered using -50 edo dram with 20 ns page cycle time and a 50 mhz memory clock, yielding a 400mb peak bandwidth. the MX86250 is capable of even higher memory clock speed. as faster edo dram (-35 with 15ns page mode cycle time) enters volume production, the MX86250 will deliver 533 mb/sec bandwidth which is comparable to premium priced drams such as 66 mhz sgram / sdram, or rambus rdram. the center of the memory controller is an intricate arbi- ter which receives memory access requests from the graphics co-processor for bitblt cycles, the display con- troller for screen fetch, the video processor for video play- back, the pci bus interface for cpu access, the hard- ware cursor for cursor bitmap fetch, and the dram re- fresh cycle request. the arbiter allocates memory cycles according to priority. for example, the display processor has higher priority than the graphics co-processor. a 32-level 64-bit fifo is implemented to buffer the pixels fetched from display memory for the screen refresh and video playback. the fifo entries can be flexibly allocated between three different processors: graphics, video line 1 and video line 2. this flexibility works to optimize per- formance across various screen resolutions and video playback operations. the memory controller generates all dram cycles. its logic is carefully designed to optimize dram cycle tim- ing parameters. for example, the dram entry cycle which is the time from ras precharge to the end of first cas cycle is optimized to the minimum of 4 clock cycles, ver- sus the commonly seen 5 or 6 clock cycles in other gui chips. another example is that of edo dram read cycle. the MX86250 eliminates the one extra clock cycle at the end of page mode cycles. unified memory architecture the MX86250 fully supports the vesa unified memory architecture (vuma) standard. the memory controller implements the vuma standard rq/gnt state machine which supports two request priorities. bus parking is pro- vided to minimize bus switch overhead. dram read and write operations in uma mode can have programmable number of wait states to accommodate the wide varia- tion in main system dram module access speed. in ad- dition, the dram interface drivers have programmable drive strength to work with wide range of dram inter- face loading on system motherboards. 2.4 pci bus interface unit the MX86250 bus interface unit (biu) implements a glueless connection to industry standard pci local bus which is compliant with windows 95 plug'n'play require- ment. pci bus speed can be up to 33 mhz. for peak transfer rate between host cpu and the MX86250, zero wait state pci burst cycles are supported. the resultant 133 mb per second bandwidth greatly enhances the performance level of graphics intensive software such as windows gui and autocad that do lots of direct accesses to video memory. the biu has an 8 level command and data fifos to buffer host transfers and enables concurrent operations of the host cpu, the graphics engine and the video processor. the pci rev. 2.1 disconnect and retry protocol is fully supported eliminating the delays of host cpu polling for biu fifo status.
6 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 2.5 video processor the MX86250 video processor accelerates the playback of avi or mpeg video decoded by a software codec such as cinepak, indeo, or mpeg-1. profiling of the task load showed that about one third time each is spent in de- compression, color conversion and pixel transfer to screen. the video processor implements the color con- version and pixel transfer in hardware, leaving only the decompression task to cpu. thus, the video play frame rate which used to be 8 to 10 fps from software codec is approximately tripled to the full motion rate of 30 fps by the MX86250. video clips are typically in qcif or cif format which are relatively small when viewed on the svga display. it is very desirable to scale up the video window to at least 640x480 or even full screen at 1024x768. the scale up can be just duplicating the pixels (zoom) which produces blocky pictures. in high end broadcast quality video pro- cessing, a smoothing filter is typically used to remove the blocky artifacts. the MX86250 video processor imple- ments both scaler and smoothing filters so that full mo- tion video can play in full screen without degradation. horizontal and vertical interpolation the video processor performs the filtering in both hori- zontal and vertical dimension. while most first genera- tion video chips only have one horizontal filter. the MX86250 provides three filters to fit the particular needs of different video decoders. the vertical interpolation fil- ter further enhances the appearance of video images by eliminating staircasing diagonal lines and illegible text commonly seen in video played by 1 st generation video chips. pixel formats the video processor supports many pixel formats. the video pixels can be in rgb formats such as krgb- 1.5.5.5, rgb-5.6.5, xrgb-8.8.8. the krgb has 1 key bit which works as a color key. more likely, the video pix- els are in yuv format such as yuv-16 (4:2:2), yuv-8 (2:1:1), or ycbcr-16 (4:2:2). the yuv format pixel has a range of value from 0 to 255, while the ycbcr format pixel values are in the range of 16 to 240. direct draw feature support the video processor fully support windows 95 direct draw with features such as chroma key, page flipping and blending. the chroma key is designed for blue screen video which is very useful in games where video sprites are employed. the new indeo 4.0 transparency feature also makes heavy use of the chroma key mechanism. the video window can be double-buffered to avoid tear- ing. the video processor executes page flipping in syn- chronization with vertical blanking. a status bit is pro- vided to inform software of the completion of page flip- ping. edge blending the MX86250 edge b lending is an unique new feature. it is implemented to enhance the edge quality of chroma keyed video sprites. directdraw does provide api calls which support the use of edge blending. the blending feature provides 16 levels of alpha mixing of the video and graphics window. this can be used to do a very smooth dissolve or fade which are popular visual effects often used in edutainment titles. 2.6 media port the media port is a direct interface to mpeg and video decoders. a MX86250 based graphics card can deliver very extensive multimedia functionality by fully utilizing the media port. an mpeg-1 decoder chip can be incor- porated on board to deliver higher quality mpeg video. video front end such as the philips sa7110 can be built in for video capture and live tv window. the media port can accept pixel data streams from ei- ther the pixel port or the pci bus interface. the pixel data stream pass through a fifo before it gets written into the frame buffer. a flexible decimation unit can be used to reduce the input video frame size C usually required for capturing camera input. the video window for media port video stream is also double buffered for anti-tearing. interlaced video input can be captured in two ways: one field only, or converted to non-interlaced frame.
7 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 vmi connector to support a wide variety of video and mpeg decoders, the media port supports the vmi ( video module inter- face) standard. the vmi specifies a 40-pin connector which, in addition to the vga connector, contain an 8-bit yuv pixel bus and an 8-bit host data bus. the pixel bus transfers 8-bit packed format yuv pixels from video de- coders to the media port. the host bus transfers com- pressed mpeg data stream from the media port to the mpeg decoder chip. a small daughter card carrying the decoder chip plugs into the 40 and 26 pin connectors. to support the philips 7110 chip 16-bit yuv pixel format. the MX86250 media port has a special mode where the vmi host bus pins are used for the upper 8 bits of yuv pixels. 2.7 true color ramdac the MX86250 internal 24 bit ramdac provides three 256-entry 6-bit word color look-up table (lut) rams feed- ing three 8-bit dacs for 8-bit per pixel modes. a clock doubled mode is also provided. a 24 bit lut bypass is used in high color (15/16 bits/pixel) and true color ( 24 bits/pixel) modes. the ramdac works at pixel clock rate up to 160 mhz. many high resolution display modes are possible at this high pixel clock rate. for example, with a 2 mb card, the following video mode provides flicker free displays, 1280x1024, 256 color, @80 hz 1024x768, 64k color, @120 hz 800x600, 16m color, @120 hz 2.8 dual clock synthesizers the MX86250 contains two phase locked loop (pll) fre- quency synthesizers. they generate the dot clock (dclk) for display logic and memory clock (mclk) for memory controller and graphics engine. each pll scales the input reference frequency to a pro- grammed clock frequency. the reference frequency comes from either the crystal oscillator across the xin and xout pin or from a clock input from xin pin. the pll generate its output clock frequency based on two programmed values, the m and n value, and accord- ing to the following formula : f out = f ref * (m+2) / (n+2) * 2 r where r is the 2 bit scale value. 2.9 peripheral interface ports the MX86250 has interface ports designed to support the vesa ddc monitor interface, the i 2 c channel, and serial eeprom. vesa ddc standard the vesa ddc (display data channel) standard speci- fies a two pin serial channel between the display monitor and the graphics controller. the display monitor sends its capability and configuration datum to the graphics con- troller chip for the display driver to set up video display mode accordingly. windows 95 plugnplay interface for display monitors is based on the ddc standard. the MX86250 provides fully compliant implementation of the ddc using the dd0 and dd1 pin. i 2 c and eeprom support the i 2 c channel is also a two pin serial bus as defined by philips. many video components such as the sa7110 video decoder relies on the i 2 c channel. the MX86250 provides the sck and sda pin for interface to i 2 c chan- nel. some graphics cards are designed to store certain card configuration or setup information in non-volatile memory storage. the MX86250 can support such a card using serial eeprom. the dd0 and dd1 pin can be pro- grammed to form an interface to serial eeprom chips.
8 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 2.10 power-on reset strapping md[3:0]: rastctrl[3:0] these 4 bits are used for ras precharge/low timing con- trols. the selection is listed below : rastctrl[3:0] ras precharge ras low (in mclk) (in mclk) 0000 3.5 5.5 0001 3.5 4.5 0010 3.5 3.5 0011 2.5 4.5 0100 2.5 3.5 0101 2.5 2.5 0110 1.5 3.5 0111 1.5 2.5 1000 3 6 1001 3 5 1010 3 4 1011 2 5 1100 2 4 1101 2 3 1110 reserved reserved 1111 reserved reserved md[5:4]: dramcyc[1:0] dramcyc[1:0] dram cycles 00 2 cycles fast page dram cycle 01 2 cycles edo dram cycle 10 1 cycles edo dram cycle 11 reserved md6: dualcas 0--dual we dram 1--dual cas dram md7: enuma 0--disable uma 1--enable uma md8: reserved md9: reserved md10: ma9outse this is used to select ma9 output pin if uma is enabled. 0--ma9 output through web1 1--ma9 output through oeb md11: reserved md12: extmclk 0--use internal mclk 1--use external mclk. for uma, external mclk will come from cpu clock. md13: extdclk 0--use internal dclk 1--use external dclk md14: fc8 0--16-bit or no feature connector 1--8-bit feature connector md15: enstvw 0--stereo view off. 1--enable stereo view. dd1 is used for stereo view control. dd1 is high for odd field, low for even field during interlaced display. for non-interlaced display, dd1 is always low. md16: retryoff 0--enable bus retry. 1--disable bus retry. md17: cromretryoff 0--enable disconnect function for configuration and rom accesses. 1--disable disconnect function for configuration and rom accesses.
9 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 2.11 pin description pci bus interface pins: pin name pin no. type description rstb# 178 i this input is pci bus reset#, it is an active low signal used to initialize the gui to a known state. the trailing edge of this input loads the power on strapping inputs through md0 to md17. the power on strapping input pins each has an internally weakly pulled down resistor (about 50k ohm). if a power on reset input status "0" is needed, then the corresponding pin doesn need an externally pulled up resistor. if a power on reset input status "1"is needed, then the corresponding pin must be pulled up by a 10k ohm resistor. cpuclk 167 i this input is the pci bus clock. it is an 1x clock of 33mhz. frameb 173 i this input is frame#, it is low to indicate the gui that a valid address is present on the pci address bus and a new bus cycle or burst bus cycles are starting. when sampling this signal low, gui would latch the address and bus commands. irdyb 170 i this input is initiator rdy#, it is generated from an pci bus master. when it is low, irdyb indicates that the initiator is able to complete the current bus transaction if and only if the trdy# is also low. trdyb 171 sto this output is target rdy#, it is generated by gui if the current bus cycle belongs to the gui. when it is low, trdy# indicates that the gui is able to complete the current bus transaction which already targeted onto it if and only if the irdy# is also low. it remains low until this current cycle ends, then goes into high for one pci clock cycle, after that then goes into tri-state. devselb 169 sto this output is devsel#. when driven low, it indicates that gui will respond to the current cycle. it remains low until this current cycle ends, then goes into high for one pci clock cycle, after that then goes into tri- state. stopb 172 sto this output is stop#. when driven low, it indicates that gui will request the current bus master to stop the current bus transfer. there are two configurations about this signal. one is called disconnect. under this configuration, gui will complete the current transaction as the last one. in this case, stop# will be active at the same time that trdy# is active. the other configuration is called retry. in this case, gui just request the bus master to terminate the current cycle and retry again. trdy# will not be generated in this cycle. once asserted, it remains low until this current cycle ends then goes into high for one pci clock cycle, after that then goes into tri-state.
10 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description par 174 to this output is par. it is only driven during pci bus master doing read accesses from gui. when driven, it will provide an even parity across the ad[31:0], and c/be#[3:0]. this signal is an tri-state output. intrb 168 to this output is inta#. it is and interrupt request signal to system interrupt controller. this signal always hard wired to the pci bus inta# signal pin. it is an open drained output. this pin is typically unused in display subsystem design, but may be connected to irq9 via pci configuration register. idsel 181 i this input is idsel. it is used as an initialization device select during pci bus auto-configuration cycles. when high, it indicates that gui is now selected as a target for pci bus configuration cycles. cbe0# 180 i this multiplexed input is part of a pci bus command definition or a byte enable for byte lane 0. during address phase of a pci bus transaction, it defines the command. during data phase of a pci bus transaction, it defines if byte lane 0 is engaged in the transfer or not. cbe1# 179 i this is bit 1 of bus command and byte enable. cbe2# 177 i this is bit 2 of bus command and byte enable. cbe3# 175 i this is bit 3 of bus command and byte enable. the pci bus commands supported are listed below: c\be[3:0]# pci bus command type 0000 (interrupt acknowledge) 0001 (special cycle) 0010 i/o read 0011 i/o write 0100 reserved 0101 reserved 0110 memory read 0111 memory write 1000 reserved 1001 reserved 1010 configuration read 1010 configuration write 1100 memory read multiple 1101 (dual address cycle) 1110 memory read line 1111 memory write and invalidate pci bus interface pins:(continued)
11 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description ad0 41 i/o ad[31:0] is the multiplexed address and data bus for pci, which 32-bit wide. ad1 40 ad2 38 ad3 37 ad4 36 ad5 35 ad6 34 ad7 33 ad8 32 ad9 31 ad10 29 ad11 28 ad12 27 ad13 26 ad14 25 ad15 24 ad16 23 ad17 22 ad18 20 ad19 19 ad20 18 ad21 17 ad22 16 ad23 15 ad24 14 ad25 13 ad26 12 ad27 10 ad28 9 ad29 8 ad30 7 ad31 6 pci bus interface pins:(continued)
12 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 dram interface pins: pin name pin no. type description rasb0 95 to this output is ras0#, it is the ras address strobe for bank 0, i.e. the first 2mb of 4mb dram memory. dual cas or dual we of fast page or edo dram can be supported.in uma interface, this output will be tristated if gui is not granted to access the memory bus. rasb1 98 to this output is ras1#, it is the ras address strobe for bank 1, i.e. the second 2mb of 4mb dram memory. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb0 82 to for dual cas dram type configuration, this output is cas0#. it is the cas address strobe of byte lane 0. for dual we dram type configuration, this output is we0#, it is the we# control signal of byte lane 0. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb1 81 to for dual cas dram type configuration, this output is cas1#. it is the cas address strobe of byte lane 1. for dual we dram type configuration, this output is we1#, it is the we# control signal of byte lane 1. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb2 80 to for dual cas dram type configuration, this output is cas2#. it is the cas address strobe of byte lane 2. for dual we dram type configuration, this output is we2#, it is the we# control signal of byte lane 2. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb3 79 to for dual cas dram type configuration, this output is cas3#. it is the cas address strobe of byte lane 3. for dual we dram type configuration, this output is we3#, it is the we# control signal of byte lane 3. in uma interface, this output will be tristated if gui is not granted to access the memory bus.
13 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description casb4 101 to for dual cas dram type configuration, this output is cas4#. it is the cas address strobe of byte lane 4. for dual we dram type configuration, this output is we4#, it is the we# control signal of byte lane 4. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb5 102 to for dual cas dram type configuration, this output is cas5#. it is the cas ad dress strobe of byte lane 5. for dual we dram type configuration, this output is we5#, it is the we# control signal of byte lane 5. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb6 103 to for dual cas dram type configuration, this output is cas6#. it is the cas ad dress strobe of byte lane 6. for dual we dram type configuration, this output is we6#, it is the we# control signal of byte lane 6. in uma interface, this output will be tristated if gui is not granted to access the memory bus. casb7 104 to for dual cas dram type configuration, this output is cas7#. it is the cas address strobe of byte lane 7. for dual we dram type configuration, this output is we7#, it is the we# control signal of byte lane 7. in uma interface, this output will be tristated if gui is not granted to access the memory bus. web0 94 to for dual cas dram type configuration, this output is we0#. it is the we# control signal of bank 0. for dual we dram type configuration, this output is cas0#, it is the cas address strobe of bank 0. in uma interface, this output will be tristated if gui is not granted to access the memory bus. dram interface pins:(continued)
14 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description web1 97 to for dual cas dram type configuration, this output is we1#. it is the we# control signal of bank 1. for dual we dram type configuration, this output is cas1#, it is the cas address strobe of bank 1. in uma interface, this output will be tristated if gui is not granted to access the memory bus. if gui is granted, this has the above function when ma9outse is 1. if ma9outse is 0, it is the ma9, which is necessary for asymmetrical dram. oeb 99 to this output is oe#, it is the oe# control signal for both banks of dram. in uma interface, this output will be tristated if gui is not granted to access the memory bus. if gui is granted, this has the above function when ma9outse is 0. if ma9outse is 1, it is the ma9, which is necessary for asymmetrical dram. ma0 83 to the outputs ma[8:0] is the dram memory address bus for both banks. ma1 84 it is used to pass the ras address and cas address to drams. in uma interface, ma2 85 these outputs will be tristated if gui is not granted to access the memory bus. ma3 87 ma4 88 ma5 89 ma6 90 ma7 91 ma8 92 md0 78 i/o md[7:0] is the dram data bus of memory plane 0 of bank 0 or bank 1. md1 77 in bios rom accesses, these are the data inputs[7:0] of external rom. md2 76 they are also served as power-on strapping inputs. md3 75 md4 74 md5 72 md6 71 md7 70 dram interface pins:(continued)
15 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description md8 69 i/o md[15:8] is the dram data bus of memory plane 1 of bank 0 or bank 1. md9 68 they are also served as power-on strapping inputs. md10 67 md11 66 md12 64 md13 63 md14 62 md15 61 md16 60 i/o md[23:16] is the dram data bus of memory plane 2 of bank 0 or bank 1. md17 59 md[17:16] are also used as power-on strapping inputs. md18 58 md19 56 md20 55 md21 54 md22 53 md23 52 md24 51 i/o md[31:24] is the dram data bus of memory plane 3 of bank 0 or bank 1. md25 50 in bios rom accesses, md[31:16] are the address outputs[15:0] for external md26 49 rom. md27 47 md28 46 md29 45 md30 44 md31 43 md32 105 i/o md[39:32] is the dram data bus of memory plane 4 of bank 0 or bank 1. md33 106 md34 107 md35 108 md36 109 md37 110 md38 111 md39 112 dram interface pins:(continued)
16 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description md40 114 i/o md[47:40] is the dram data bus of memory plane 5 of bank 0 or bank 1. md41 115 md42 116 md43 117 md44 118 md45 119 md46 120 md47 121 md48 122 i/o md[55:48] is the dram data bus of memory plane 6 of bank 0 or bank 1. md49 124 md50 125 md51 126 md52 127 md53 128 md54 129 md55 130 md56 131 i/o md[63:56] is the dram data bus of memory plane 7 of bank 0 or bank 1. md57 133 md58 134 md59 135 md60 136 md61 137 md62 138 md63 139 dram interface pins:(continued)
17 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 uma interface pins: pin name pin no. type description smurqb 182 o this is the mreq# signal for vesa uma interface. gui uses this signal to request memory accesses on uma. smgntb 183 i this is the mgnt# signal from vesa uma interface. gui will drive dram interface signals when this signal is active in uma configuration. rom bios interface pins: pin name pin no. type description romoeb 42 o this output is romoe#. it may be connected to either one or both of the bios rom chip select and output enable pins directly. internal vcg related interface pins: pin name pin no. type description xi 157 i this input is used as a reference frequency input for internally implemented oscillator. an external crystal or oscillator of 14.318mhz may be used. if an external crystal is used, it must be connected between xin and xout. if an external oscillator is used, it must connect to xin. in this case, the xout must be left open. xo 158 o this is used as a reference frequency output for internally implemented oscillator. if an external crystal is used, it must be connected between xin and xout. if an external oscillator is used, the xout must be left open.
18 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 internal ramdac related interface pins: pin name pin no. type description svref 4 i this pin is the voltage reference of 1.2v for internal dac and monitor sence logic. it must be connected with a 0.1u capacitor to avcc of ramdac. scomp 161 i this pin is the compensation input for internal dac. it must be connected with a 0.1u capacitor to avcc of ramdac. siref 2 i this pin is the current reference. sr 206 o this pin is the analog output of the pixel color red component to monitor. it has a voltage level of 0.0v(blank) to 0.7v(full scale) when terminated with 75 ohm double loads. sg 207 o this pin is the analog output of the pixel color green component to monitor. it has a voltage level of 0.0v(blank) to 0.7v(full scale) when terminated with 75 ohm double loads. sb 208 o this pin is the analog output of the pixel color blue component to monitor. it has a voltage level of 0.0v(blank) to 0.7v(full scale) when terminated with 75 ohm double loads. media port and feature connector related interface pins: pin name pin no. type description p0 141 io p[7:0] is the pixel or video data bus from/to external feature connector or video p1 142 module interfaces. p2 143 p3 144 p4 145 for 8-bit feature connector or vafc, this is a bidirectional pixel data bus. p5 146 when evideo# is low, it functions as inputs. the pixel data from external display p6 147 or video card will be passed to the internal ramdac for display. p7 148 if evideo# is high, the internal ramdac uses pixel data internally generated for display. in this case, if pa output control for dpms, which is defined in bit 6 of register 3?5/26, is set to normal operation, gui will drive out pixel data. otherwise, it will tristate the output. if vmi is used, p[7:0] is the video data inputs. this chip supports saa7110 video decoder and cl480 mpeg decoder interfaces. for saa7110 interfaces, p[7:0] is the lower byte of the 16-bit video data inputs. for cl480 interfaces, it's the 8-bit video data inputs.
19 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description p8 187 io p[15:8] is the pixel data bus from/to external feature p9 188 io connector or host data bus from/to vmi. p10 190 io p11 191 io for vafc or 16-bit feature connector, p[15:8] functions as pixel output or video p12 192 io input. when evideo# is low, it is used for video input, which will be passed to p13 193 io the internal ramdac for display. if evideo# is high, the internally generated p14 194 io pixel data will be driven out to video card if pa output control for dpms p15 195 io is set to normal operation. if vmi is used, p[15:8] is used as the host data bus, which is bidirectional. through this bus, cpu can access the vmi module. for saa7110 interfaces, p[15:8] is the higher byte of the 16-bit video data inputs. for cl480, its the 8-bit host data bus, which is inputs in read cycles, and outputs in write cycles. pclk 150 io this is the pixel clock input/output pin. for 8-bit feature connector, it is an input when evideo# is low. in this case, it is used for internal ramdac display. when evideo# is high, the internally generated pixel clock is driven out through this pin. for vafc, it's always an pixel clock output. the internal pixel clock for ramdac is also driven to this pin. for vmi connection, pclk is always put in tri-state. ramdac use internal pixel clock for display. if external dclk is used, only 8-bit feature connector configuration is allowed, i.e. other video interfaces are not applicable. **** shouls be divided by 8 in test mode, this is the dclk output from internal vcg. sevideob 151 i this is the evideo# pin used as bidirection control for 8-bit feature connector or vafc interfaces. when set to 1, gui will drive p[15:0], blank#, hsync, vsync and pclk to the feature connector. when set to 0, all of these signal pins are tri-stated. if video interface is enabled, i.e. either saa7110 or cl480 is used for video data input, this pin loses its function. extvclk 152 i this is the video clock input pin for video interface and vafc. if external dclk is used, it is taken for external pixel clock input. in that case, video interface and vafc are not allowed. media port and feature connector related interface pins:(continued)
20 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description blankb 154 io this is a multi-function pin. for 8-bit feature connector or vafc, when evideo# is high, the internal blank# signal is used to control ramdac display. in this case,it is an output pin if the blank control for dpms, which is defined in bit [1:0] of register 3?5/26, is not set to 11. otherwise, it will be tri-stated. when evideo# is set to 0, it's an input from feature connector. gui uses it to control ramdac display. for vmi or saa7110, its the href input. and for cl480 it's the hsync# input. in either case, it indicates that video data of a scanline is coming in. hsyncb 155 to it's the hsync# output pin, which is the horizontal sync to analog monitor. for 8- bit feature connector or vafc, it is enabled when evideo# is high and hsync control for dpms, which is defined in bit [3:2] of register 3?5/26, is set to value other than 11. otherwise, it is tri-stated. but if either saa7110 or cl480 is select, it is enabled also. vsyncb 156 to it's the vsync# output pin, which is the vertical sync to analog monitor. for 8-bit feature connector or vafc, it is enabled when evideo# is high and vsync control for dpms, which is defined in bit [5:4] of register 3?5/26, is set to value other than 11. otherwise, it is tri-stated. but if either saa7110 or cl480 is select, it is enabled also. l4vs 198 io if external vcg is selected, this pin is used as one of the mclk select output, mcsel1. mcsel[2:0] is used to select mclk frequency from external vcg. if internal vcg is used, it is an input pin for video interface. its the vref for vmi, vs for saa7110 and vsync# for cl480. either one indicates that its the frame start of input video data. sck 5 io it's the i 2 cclk input/output pin for both saa7110 interface or ddc2 monitor control. as an input, the i 2 c clk value can be monitored by reading bit 2 of the memory-mapped register port at offset 31c or bit 2 of the i/o register at 3?5/50. to generate clock pulses, software can just program either bit 0 of the above memory- mapped register or bit 5 of the io register at 3c4/1e. if 0 is programmed, this pin is pulled low. if 1 is programmed, this pin is tri-stated. with the external pull-up, it makes i2 cclk go to high state. in this way, clock pulses are generated. media port and feature connector related interface pins:(continued)
21 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description l4sda 204 io this is a multi-function pin. if external vcg is selected, this pin is used as of the mclk select output, mcsel2. otherwise, it is the serial data input/ouput pin for i 2 c bus. as an input, it can be monitored by reading bit 3 of the memory-mapped register at offset 31c, or of the i/o port at 3?5/50. to generate data, software can program either bit 1 of the above memory-mapped register or bit 6 of the i/o register at 3c4/1e. l4hsel0 200 o this is a dual-function pin. if external dclk is selected, this pin is used as one of the dclk select output, vcksel0. vcksel[3:0] is used to select dclk frequency from external vcg. otherwise, it is used as ha0 for vmi or hsel0 for cl480. ha[2:0] and hsel[2:0] are the host address bus for vmi and cl480 individually. l4hsel1 202 o this is a dual-function pin. if external dclk is selected, this pin is used as one of the dclk select output, vcksel1. otherwise, it is used as ha1 for vmi or hsel1 for cl480. l4hsel2 202 o this is a dual-function pin. if external dclk is selected, this pin is used as one of the dclk select output, vcksel2. otherwise, it is used as ha2 for vmi or hsel2 for cl480. l4rwb 203 o this is a dual-function pin. if external dclk is selected, this pin is used as one of the dclk select output, vcksel3. otherwise, it is used as r/w# for vmi or cl480. in that case, it controls the host read/write with them. for read cycles, it is driven high, for write cycles, it is driven low. l4dsb 197 o it is a dual-function pin. if external vcg is selected, it is used as one of the mclk select output, mcsel0. otherwise, it is used as ds# for vmi or cl480. gui pulls it low to select vmi target or cl480 for read/write operation. cflevel 153 i it is the cflevel input from cl480 or odd from saa7110 or the mclk input if external mclk is selected. as the cflevel from cl480, it indicates that the cl480 coded data fifo for compressed data is going to be exhausted. gui will generate the interrupt signal to inform the software to put more compressed data into cl480. when used as the odd signal from saa7110, it is an odd/even field indication for interlaced video. when high, it is odd field, otherwise, even field. gui uses this to determine the memory location for incoming video data. media port and feature connector related interface pins:(continued)
22 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 pin name pin no. type description dd0 184 io it is a dual-function pin. if cl480 or vmi interface is enabled, it is the dtack# input, which is the host data acknowledge from them. when set to 0, it indicates that cl480 or vmi target is ready for data receiving or output. gui can thus complete the cycle. if not the above case, it is a general data i/o pin. it can be read through bit 0 of io port 3?5/50. as an output, it's in tristate normally. write to i/o register 3c2, 3c5/1d or 3c5/1e will enable it. bit 3 of 3c5/1e is selected as its output value. dd1 185 io it is a dual-function pin. when stereo view is enabled, it is used as the stereo view control output. during interlaced display, it is high for odd field and low for even field. for non-interlaced display, it is always driven low. it is also a general data input/output pin. as an input, it can be read through bit 1 of io port 3?5/50. to use it as an output, i/o registers 3c2, 3c5/1d or 3c5/1e should be written. it then leaves tristate and select bit 4 of 3c5/1e as its output value. stb 186 o this is the data write strobe for external devices when dd[1:0] are used as general data input/output pins. it is used to latch dd[1:0] driven by gui. it is high when i/o registers 3c2, 3c5/1d or 3c5/1e is written or power-on reset completes. if external vcg is used, it is used to latch vcksel[3:0]. the external vcg will use these values to generate expected frequencies of dclk. strdb 196 o this is the data read enable for external devices when dd[1:0] are used as general data input/output pins. the external devices should drive dd[1:0] when this signal is low. otherwise, put them to tri-state. media port and feature connector related interface pins:(continued)
23 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 power pins: pin name pin type pin no. drive(ma) c_load(pf) vddp - 11,57,123, 164,199, - - gndp - 21,48,65,73,100,113,140, 149,176, 189 - - vdd - 30,93,165 gnd - 39,86,96,132,166 - - avdd - 1,159, 163 avss - 3,160, 162,205
24 MX86250 p/n:pm0387 rev. 1.1, jul 26, 1996 2.12 pinout configuration 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 xi xo vdd gnd scomp gnd vdd vddp vdd gnd cpuclk intr devsels irdyb trdyb stopb frameb pa r cbeb3 gndp cbeb2 rstb cbeb1 cbeb0 idsel smurqb smgntb dd0 dd1 stb p8 p9 gndp p10 p11 p12 p13 p14 p15 strdb l4dsb l4vs vddp l4hsel0 l4hsel1 l4hsel2 l4rwb l4sda gnd sr sg sb 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 casb7 casb6 casb5 casb4 gndp oeb rasb1 web1 gnd rasb0 web0 vdd ma8 ma7 ma6 ma5 ma4 ma3 gnd ma2 ma1 ma0 casb0 casb1 casb2 casb3 md0 md1 md2 md3 md4 gndp md5 md6 md7 md8 md9 md10 md11 gndp md12 md13 md14 md15 md16 md17 md18 vddp md19 md20 md21 md22 vdd siref gnd svref sck ad31 ad30 ad29 ad28 ad27 vddp ad26 ad25 ad24 ad23 ad22 ad21 ad20 ad19 ad18 gndp ad17 ad16 ad15 ad14 ad13 ad12 ad11 ad10 vdd ad9 ad8 ad7 ad6 ad5 ad4 ad3 ad2 gndp ad1 ad0 romoeb md31 md30 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 156 155 154 153 152 151 150 149 148 147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 vsyncb hsyncb blankb cflevel extvclk sevideob pclk gndp p7 p6 p5 p4 p3 p2 p1 p0 gndp md63 md62 md61 md60 md59 md58 md57 gnd md56 md55 md54 md53 md52 md51 md50 md49 vddp md48 md47 md46 md45 md44 md43 md42 md41 md40 gndp MX86250 md39 md38 md37 md36 md35 md34 md33 md32 md29 md28 md27 gndp md26 md25 md24 md23
m acronix i nternational c o., l td. headquarters: tel:+886-3-578-8888 fax:+886-3-578-8887 europe office: tel:+32-2-456-8020 fax:+32-2-456-8021 japan office: tel:+81-44-246-9100 fax:+81-44-246-9105 singapore office: tel:+65-747-2309 fax:+65-748-4090 taipei office: tel:+886-3-509-3300 fax:+886-3-509-2200 m acronix a merica, i nc. tel:+1-408-453-8088 fax:+1-408-453-8488 chhicago office: tel:+1-847-963-1900 fax:+1-847-963-1909 http : //www.macronix.com macronix international co., ltd. reserves the rignt to change product and specifications without notice. MX86250 25

▲Up To Search▲

Price & Availability of MX86250

	To Download MX86250 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .